Skip to content

Conversation

@forsyth2
Copy link
Collaborator

Bump to 3.1.0rc3

@forsyth2 forsyth2 self-assigned this Oct 28, 2025
@forsyth2 forsyth2 added the Update version Code specifically to update the version label Oct 28, 2025
@forsyth2 forsyth2 merged commit 05acfd8 into main Oct 28, 2025
6 checks passed
@forsyth2 forsyth2 deleted the v3.1.0rc3 branch October 28, 2025 21:22
@forsyth2
Copy link
Collaborator Author

zppy rc3

Release process notes:

Step 1: testing

cd ~/ez/zppy
git status
# branch fixes-for-rc3
# nothing to commit
git fetch upstream main
git checkout main
git reset --hard upstream/main
git log
# Last commit: Fixes for rc3 (#753)
# Good, matches https://github.com/E3SM-Project/zppy/commits/main
rm -rf build
lcrc_conda # Activate conda
conda clean --all --y
conda env create -f conda/dev.yml -n zppy-main-20251028
conda activate zppy-main-20251028
python -m pip install .
pytest tests/test_*.py
# 35 passed in 1.13s

We will do full integration testing during the Unified testing.

Step 2: Bump versions

Step 2a: Confluence

Update https://e3sm.atlassian.net/wiki/spaces/DOC/pages/129732419/Packages+in+the+E3SM+Unified+conda+environment:

  • E3SM Unified 1.11.0: zppy v3.0.0
  • E3SM Unified 1.11.1: zppy v3.0.0
  • E3SM Unified 1.12.0: zppy v3.1.0 (We updated this when we made rc1)

Step 2b: zppy repo

cd ~/ez/zppy
git status
# Check for uncommitted changes
git fetch upstream main
git checkout -b v3.1.0rc3 upstream/main
tbump 3.1.0rc3 --no-tag
git log
# Last commit: Bump to 3.1.0rc3
# Creates commit, but doesn't push it (because branch isn't named `main`)
git push upstream v3.1.0rc3
# Follow example of https://github.com/E3SM-Project/zppy/pull/740, https://github.com/E3SM-Project/zppy/pull/750
# Create, add "Update version" label" to, and merge https://github.com/E3SM-Project/zppy/pull/754

git checkout main
git fetch upstream
git reset --hard upstream/main
git tag -a v3.1.0rc3 -m "v3.1.0rc3"
# Delete the branch from the tbump step. Otherwise, the push command won't work.
git branch -D v3.1.0rc3
git push upstream v3.1.0rc3

v3.1.0rc3 now appears on Tags but not on Releases. Good, this is expected.

Step 2c: zppy-feedstock repo

cd ~/zppy-feedstock
curl -sL https://github.com/E3SM-Project/zppy/archive/v3.1.0rc3.tar.gz | openssl sha256
# SHA2-256(stdin)= b350bc2db8cf2fe0e6ea9ae5f7f96351eef116e1338d2948002fca01a62f9e3d
git status
# branch v3.1.0rc2
# nothing to commit
git fetch upstream dev
git checkout -b v3.1.0rc3 upstream/dev
emacs recipe/meta.yaml
# In `recipe/meta.yaml`, update the version and sha256 (and the build number if needed):
# {% set version = "3.1.0rc3" %}
# sha256: ... # The sha256 from the previous step
# number: 0 # build >>> number should always be 0

# Do we need to edit any dependencies?
# Visit https://github.com/E3SM-Project/zppy/compare/v3.1.0rc2...v3.1.0rc3
# There are no changes to conda/ or /.github directories
# So we don't need to change anything here

git add -A
git commit -m "v3.1.0rc3"
git push forsyth2 v3.1.0rc3
# Follow example of https://github.com/conda-forge/zppy-feedstock/pull/27, https://github.com/conda-forge/zppy-feedstock/pull/28

Created conda-forge/zppy-feedstock#29

New in this rc

For reference, this adds the following PRs on top of rc2:

@forsyth2 forsyth2 mentioned this pull request Oct 28, 2025
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Update version Code specifically to update the version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants